-
Subprocesses determine tools.
The approach supports people doing their jobs as they see it. Forcing
additional tools on people only adds more burdens to their jobs and
they will likely ignore them. Additional requirements should be
integrated into existing subprocesses.
-
Everyone's subprocesses should be supported as best as possible. The approach supports people seeing their jobs differently. This is often a good thing for
subprocess improvement.
-
Tools are role-based so that data is collected during subprocess execution. As people partake in the subprocesses, the approach supports data entry in the
system. If data collection is done after the fact, the quality of the
data generally suffers.
-
Tools are people-based so that users require minimal training. The approach helps people to determine which steps to use. For each
of the substeps (i.e., forms and documents), the approach should have clear
templates, instructions, and samples.
-
Tools are web-based so that users can easily partake. The web-based approach supports the reduced need to install special software on user's computers. This is especially important in the case where
the number of participants is large.
-
Everyone helps build the tools. The approach supports joint ownership in the subprocesses and the underlying systems which is crucial for overall acceptance.